Systems, methods and devices for determining work placement on processor cores

ABSTRACT

Apparatuses, methods and storage medium for computing including determination of work placement on processor cores are disclosed herein. In embodiments, an apparatus may include one or more processors, devices, and/or circuitry to identify a favored core of the processor cores. The one or more processors, devices, and/or circuitry may be configured to determine whether to migrate a thread to or from the favored core. In some embodiments, the determination may be by a process executed by a driver and/or by an algorithm executed by a power control unit of the processor.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims the benefit of priority to, U.S. patent application Ser. No. 17/173,100, filed Feb. 10, 2021, which is a continuation of, and claims the benefit of priority, to U.S. patent application Ser. No. 16/107,691, filed Aug. 21, 2018, which is a Continuation of, and claims the benefit of priority, to U.S. patent application Ser. No. 14/997,032, filed Jan. 15, 2016, and now issued as U.S. patent Ser. No. 10/073,718, on Sep. 11, 2018, and which is incorporated by reference in entirety.

TECHNICAL FIELD

The present disclosure relates to processor efficiency and more specifically relates to determining work placement on processor cores.

BACKGROUND

The background description provided herein is for the purpose of generally presenting the context of the disclosure. Unless otherwise indicated herein, the materials described in this section are not prior art to the claims in this application and are not admitted to be prior art by inclusion in this section.

In order to manage manufacturing variation during fabrication of multicore processors while maintaining quality and reliability, conservative guard bands are employed during testing and devices are “binned” or classified based on their speed and power characteristics. Conventional speed binning treats multicore processors as single-core devices by assigning a single related speed and minimum operating voltage for the processor as a whole. The rated speed and minimum voltage typically reflect the speed of the slowest core and the minimum voltage of the core having the poorest minimum voltage.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.

FIG. 1 illustrates an example system equipped with technology to determine work placement on processor cores, according to various embodiments.

FIG. 2 illustrates an example of the system of FIG. 1 including a driver to determine work placement on processor cores, according to various embodiments.

FIG. 3A illustrates example operations that may be performed by the application thread tracker of FIG. 2 , according to various embodiments.

FIG. 3B illustrates example operations that may be performed by the monitoring loop of FIG. 2 .

FIG. 3C illustrates example operations that may be performed by the affinitization control loop of FIG. 2 , according to various embodiments.

FIGS. 4A-B illustrate an example of pseudo code to implement a module of the Power Control Unit (PCU) of the system of FIG. 1 , according to various embodiments.

FIG. 5 illustrates an example process that may be performed by the module of FIG. 1 , according to various embodiments.

FIG. 6 illustrates another process that may be performed by the module of FIG. 1 , according to various embodiments.

FIG. 7 illustrates an example computing device that may employ the apparatuses and/or methods described herein, according to various embodiments.

DETAILED DESCRIPTION

Apparatuses, methods and storage medium associated with computing that includes determination of work placement on processor cores are disclosed herein. In embodiments, an apparatus may include one or more processors, devices, and/or circuitry to identify a favored core of the processor cores. The one or more processors, devices, and/or circuitry may be configured to determine whether to migrate a thread to or from the favored core. In some embodiments, the determination may be executed by a process performed by a driver and/or by a process executed by a power control unit of the processor.

In the following detailed description, reference is made to the accompanying drawings which form a part hereof wherein like numerals designate like parts throughout, and in which is shown by way of illustration embodiments that may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description is not to be taken in a limiting sense, and the scope of embodiments is defined by the appended claims and their equivalents.

Aspects of the disclosure are disclosed in the accompanying description. Alternate embodiments of the present disclosure and their equivalents may be devised without parting from the spirit or scope of the present disclosure. It should be noted that like elements disclosed below are indicated by like reference numbers in the drawings.

Various operations may be described as multiple discrete actions or operations in turn, in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation. Operations described may be performed in a different order than the described embodiment. Various additional operations may be performed and/or described operations may be omitted in additional embodiments.

For the purposes of the present disclosure, the phrase “A and/or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).

The description may use the phrases “in an embodiment,” or “in embodiments,” which may each refer to one or more of the same or different embodiments. Furthermore, the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.

As used herein, the term “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.

Processor cores (hereinafter, may also simply be referred to as cores) may be exposed to operating systems, typically via a firmware interface (e.g., Advanced Configuration and Power Interface (ACPI)). The operating system may create a list of logical processors and places that work on these logical processors, with one or more logical processors associated with each processor core, in accordance with the operating system's scheduler policy. As such, the operating system may decide the physical placement of software threads (hereinafter “threads”) within a processor package, e.g., on which core/logical processor the thread runs. For a variety of reasons, such as manufacturing variations, all cores are not created equal, e.g., while the cores may be logically identical (e.g., architecturally identical), they may have different physical characteristics. Cores that can operate at a higher performance level, e.g., higher frequency or lower voltage than the frequency/voltage band of the processor package may be referred to as favored cores. As such, placing work on a core without consideration of manufacturing variations and/or favored cores can result in higher power and/or lower performance.

This disclosure addresses a control process for placement of work on favored cores at the operating system at the software level (e.g., driver level), as well as the control process for placement of work on favored cores at a different level, e.g., a hardware (pcode) level.

An example process for placing work on a favored core may be implemented in operating system software (e.g., driver). The number of demanding threads, e.g., software threads, may be calculated (by virtue of per thread utilization exceeding a programmable threshold), and assigned to run on an ordered list of favored cores (for example using forced affinity). Further, dynamic adjustment may be made of workload assigned to the cores as conditions change. Threads of an application may be prioritized according to a list order provided or by virtue of the application being “in focus” (configurable).

Another example process for placing work on a favored core may include a pcode process for placing work on favored cores via Dynamic Core Migration (DCM) by examining core utilization, e.g., in terms of its c-state and p-state residency.

Utilizing favored cores first when a scheduler practices scheduling on no more cores than demand necessitates—may provide a performance and/or power benefit as the favored core may be both the highest performance core as well as the lowest voltage core.

FIG. 1 illustrates an example system equipped with technology to determine work placement on processor cores, according to various embodiments.

In at least one embodiment, system 100 may include a processor 101 having a core region 120 and an uncore 122. In some embodiments, the core region 120 may include multiple processing cores 102-1 to 102-n, but disclosed functionality may be applicable to single core processors in a multi-processor system. In some embodiments, the processor 101 may include a first processing core 102-1, a second processing core 102-2, and so forth through an n-th processing core 102-n.

In some embodiments, processing cores 102 may include sub-elements or clusters that provide different aspects of overall functionality. In some embodiments, processing cores 102 may include a front end 104, an execution pipeline 106, and a core periphery 128. The core periphery 128 may include a first level (L1) data cache 108, a storage, e.g., C-6 storage 130 (e.g., corresponding to ACPI state C-6), and an advanced programmable interrupt controller (APIC) 132. In at least one embodiment, front end 104 may be operable to fetch instructions from an instruction cache (not depicted) and schedule the fetched instructions for execution. In some embodiments, execution pipeline 106 may decode and perform various mathematical, logical, memory access and flow control instructions in conjunction with a register file (not depicted) and the L1 data cache 108. Thus, in some embodiments, front end 104 may be responsible for ensuring that a steady stream of instructions is fed to execution pipeline 106 while execution pipeline 106 may be responsible for executing instructions and processing the results. In some embodiments, execution pipeline 106 may include two or more arithmetic pipelines in parallel, two or more memory access or load/store pipelines in parallel, and two or more flow control or branch pipelines. In at least one embodiment, execution pipelines 106 may further include one or more floating point pipelines. In some embodiments, execution pipelines 106 may include register and logical resources for executing instructions out of order, executing instructions speculatively, or both. In embodiments, each core 102-1 through 102-n may be a superscalar core or a hyperthreaded core. A superscalar core can execute two or more instructions in parallel. A hyperthread core can execute two or more instruction contexts or instruction streams in parallel.

Core periphery 128 can include logic that supports front end 104 and execution pipeline 106, including managing storage and interrupts. Core periphery 128 can include data cache 108, C6 storage 130 and the advanced programmable interrupt controller (APIC) 132. C6 storage 130 can store a software context and identity (or core state) of processing core 102 when processing core 102 transitions into a low-power state (such as a C6 state). A peripheral controller (e.g., APIC 132) can manage interrupts for processing core 102, including identifying which interrupts apply to the associated processing core 102 and managing an APIC ID which can be used to identify an associated core.

In at least one embodiment, during execution of memory access instructions, execution pipeline 106 may attempt to execute the instructions by accessing a copy of the applicable memory address residing in the lowest-level cache memory of a cache memory subsystem that may include two or more cache memories arranged in a hierarchical configuration. In at least one embodiment, a cache memory subsystem may include L1 data caches 108 and a last level cache (LLC) 118 in uncore 122. In at least one embodiment, other elements of the cache memory subsystem may include a per-core instruction cache (not depicted) that operates in conjunction with front end 104 and one or more per-core intermediate caches (not depicted). In at least one embodiment, the cache memory subsystem for processor 101 may include L1 data and instruction caches per core, an intermediate or L2 cache memory per core that includes both instructions and data. LLC 118, which includes instructions and data and may be shared among multiple processing cores 102. In some embodiments, if a memory access instruction misses in L1 data cache 108, execution of the applicable program or thread may stall or slow while the cache memory subsystem accesses the various cache memories until a copy of the applicable memory address is found.

In at least one embodiment, processor 101, first processing core 102-1, second processing core 102-2 and processing core 102-n may communicate via crossbar 112, which may support data queuing, point-to-point protocols and multicore interfacing. Other embodiments of processor 101 may employ a shared bus interconnect or direct core-to-core interconnections and protocols. In at least one embodiment, crossbar 112 may serve as an uncore controller that interconnects processing cores 102 with the LLC 118. In some embodiments, uncore 122 may include cache controller 117 configured to implement a cache coherency policy and, in conjunction with a memory controller (not depicted), maintain coherency between a system memory (not depicted) and the various cache memories.

In at least one embodiment, system 100 may also include module 99, e.g., a favored core module, to determine work placement on the processor cores 102. In an example, the cores 102 may be a plurality of logically identical cores, e.g. architecturally identical cores. A first core of the plurality of cores may have a first physical characteristic and a second core of the plurality of cores may have a second physical characteristic that is different than the first physical characteristic. Module 99 may be configured to identify one of the first and second cores as favored with respect to the other of the first and second cores, e.g., by virtue of their differences in physical characteristics, such as their operating frequencies and/or voltages. Module 99 may be configured to ascertain whether to migrate a thread to or from the identified core. In an example, module 99 may be configured to control a migration of the thread to or from the identified core, e.g., to output a signal to placement controller 124, for instance.

In some embodiments, module 99 may be a component of power control unit (PCU) 124, e.g., a component of placement controller 134 of PCU 124. However, in other embodiments, module 99 may be a component separate from components of PCU 124 and/or placement controller 134. For example, in some embodiments, module 99 may be a driver associated with an operating system (FIG. 2 illustrates an embodiment including a driver 299). In such a case, an output of module 99, e.g., a determination of work placement, may be input into a scheduler of the operating system, such as the operating system of a computing device of system 100.

A power control unit may be a microcontroller or programmable state machine that consumes power related telemetry (sometimes continuously) from components on the CPU in order to manage power, frequency and temperature of the components. System 100, e.g., placement controller 134 and/or component 99, can monitor workloads of processing cores 102 and determine which work can be moved to a different core to increase efficiency. Efficiency can be measured in thermal output, power use and/or work accomplished. For example, efficiency can be increased by moving threads between cores that differ due to in-die variation (lower thermal output, decreased power usage, lifetime use management or more work performed). Efficiency can be increased by maintaining a low-voltage operation of a core by not providing a workload above a threshold (i.e., moving threads between cores to prevent a core from operating above a threshold, which is also known as “stressing” a core). Efficiency can be increased by combining multiple threads upon a single hyperthreading core, which saves power of a multi-core overhead. Efficiency can be increased by placing threads on cores that are physically separated to enable a larger spread of heat on the processor die. Efficiency can be increased by spreading heat by moving threads from physical processor to physical processor in sequence to heat different parts of a processor die. Efficiency can be increased by using cores with failed arithmetic units when instructions will not use the arithmetic units, and/or migrating threads between cores when the instructions will use the failed arithmetic units. Efficiency can be increased by performing load balancing for lifetime use management and/or thermal management.

In some embodiments, as a core is used and/or used to perform a large workload, the efficiency of the core may decrease. The efficiency decrease can be due to a larger operating voltage and/or a larger thermal output. In some embodiments, a lifetime use of cores can be managed, and workloads transitioned between cores to spread the lifetime usage of cores. In one embodiment, the processor can report a lower core count than actually available on the processor. The workload can be spread among cores to increase the overall lifetime and efficiency of the cores beyond what would be possible without the extra unreported cores. In some embodiments, threads can be transitioned off of a core to sequester the core. The sequestered core can be tested and/or determine performance characteristics of the core. In one embodiment, core sequestering can be used in conjunction with virtual machine manager solutions. In other embodiments, a sequestered core can be used to support other dedicated-purpose, hidden execution arrangements.

In some embodiments, hardware PCU 124 can decide thread placement among the core and pipeline resources available. Logical processors of the cores can be enumerated to the OS. However, the number of logical processors can be less than a number of physical cores and/or simultaneous threads supported by the processor (i.e., there can be more processor resources than are enumerated to the OS). The OS may place work on the logical processors visible to it, and the processor (e.g., the PCU 124) may at a later time migrate a thread to a different resource. For example, PCU 124 can initiate a sequence that saves the core's context, restores the context to a different core, and redirects a local APIC ID of the previous core to the new core. This migration can occur at the core or thread level. Alternatively, the hardware can provide migration hints to the OS through operating system interface 126, and the OS can move the work from one core or thread to another.

In at least one embodiment, core region 120 may include, in addition to processing cores 102, voltage regulator/clock generator (VRCG) circuits 114 for each core processor 102. In some embodiments, in conjunction with per-core supply voltage signals and clock frequency signals generated by PCU 124 and provided to each processing core 102, VRCG circuits 114 support per-core power states by applying a power state indicated by the applicable supply voltage signal and clock frequency signal to the applicable processing core 102, as well as to uncore 122.

In some embodiments, PCU 124 is further operable to select processing cores 102 for execution of specific threads and to migrate a thread and its corresponding performance objective or context information from a first core (e.g., first processing core 102-1) to a second core (e.g., second processing core 102-2), when the performance characteristics of second processing core 102-2 make second processing core 102-2 better suited to achieve a desired efficiency objective than first processing core 102-1. See, e.g., FIGS. 2 and 3 for a more detailed description of migration.

In some embodiments, processor 101 may include a hybrid assortment of cores including, in addition to processing cores 102, graphics cores and other types of core logic. In these hybrid core embodiments, PCU 124 may determine an optimal or desirable power state, not only for processing cores 102, but also for these other types of core elements in core region 120. Similarly, in at least one embodiment, processor 101 may include VRCG circuit 114-u that provides the power state for uncore 122 and, in this embodiment, PCU 124 may determine the optimal or preferred power states for uncore 122. In some embodiments, processor 101 may support individualized power states for each processing core 102, any other types of cores in core region 120, and uncore 122. Other embodiments may support one power state for the entire core region 120 and one power state for uncore 122.

PCU 124 may be also include operating system interface 126. In some embodiments, PCU 124 can provide recommendations for work placement or migration to an operating system through operating system interface 126. The operating system can then perform the thread migration between cores. For example, an operating system may not have enough information to recognize that two logical processors are actually associated with one hyperthread core. PCU 124 can recommend to the operating system that two threads be consolidated on the two logical processors, which can eliminate multi-core overhead.

FIG. 2 illustrates an example of the system of FIG. 1 including a driver to determine work placement on processor cores, according to various embodiments.

Driver 299, in embodiments, may include three function blocks, namely application thread tracker 211, monitoring loop 214, and affinitization control loop 217. Application thread tracker 211 may be configured to track all the running threads on the system for different applications. A given application can have more than one thread. As an application is running, it may create new threads and/or destroy previously created threads. Application thread tracker 211 maintains a list of all the running threads. From the maintained list, driver 299 may periodically or continuously calculate a processor core demand level of all tracked threads. FIG. 3A illustrates operations that may be performed by application thread tracker 211, to be described more fully below.

Referring again to FIG. 2 , in an example, the periodic demand calculations may be performed by monitoring loop 213 according to a configurable interval. At the interval, application thread demand checker 216 of monitoring loop 213 may calculate utilization of each processor core, e.g., a percentage from 0-100 based on core utilization by the assigned thread or threads. If demand is greater than a programmable threshold, e.g., 90 percent, then the thread/threads may benefit from a favored core. Driver 299 may identify a subset of the currently tracked threads as “demanding” threads according to the comparison to the programmable threshold. Monitoring loop 213 may include registry monitor 214 to communicate with registry 206 of operating system 205, application thread demand checker 216, and hardware configuration monitor 215 to communicate with messaging interface 223, e.g., overclocking mailbox, of CPU 222. FIG. 3B illustrates operations that may be performed by monitoring loop 213, to be described more fully below.

Referring again to FIG. 2 , affinitization control loop 217 may be configured to affinitize, using an interface exposed by the operating system (e.g., an affinity interface, an ACPI interface, or the like, or combinations thereof), a thread to a selected core, e.g., a core of a favored core list. FIG. 3C illustrates operations that may be performed by affinitization control loop 217, to be described more fully below.

Referring again to FIG. 2 , application 201 may be configured with a user interface to allow a user to select an application to be run on favored cores (threads of the user selected application may be affinitized to a favored core). Application 201, which in an example may be Intel® Turbo Boost Max App., may include foreground application detection loop 202 to check for new user selections and/or to determine which application is in focus in the operating system. In other embodiments, foreground application detection loop 202 may exist within driver 299 depending on operating system requirements.

Processer 222 may include messaging interface 223, e.g., a mailbox interface. The messaging interface may support commands to read the favored core list, which may be a ranked list that specifies a code ID (or an index) for a given core. The favored core list can be read at times to determine where in a favored core list each core belongs. Core index zero may be a most favored core, and core index N corresponding to N cores may correspond to be a least favored core. Driver 299 may use this command of messaging interface 223 to read the core list. In other embodiments, driver 299 may read the Model Specific Register (MSR) (e.g., a software visible register) of each core directly, to determine whether a core is a favored one.

In some embodiments, fuses 221 may be provided. Fuses 221 may include read only memory that is programmed at manufacturing time to indicate individually for each core an attribute of the core, e.g., its operating frequency, its voltage level. Fuses 221 store this core information, which may be read by driver 299 to determine whether a core is a favored core (which higher performance operating frequency/voltage than the frequency/voltage of the processor to which the core is a member).

Messaging interface 223 may be in communication with BIOS 207. BIOS 207 may include a user interface to enable a system administrator to manage performance configuration, e.g., overclocking, underclocking, overvolting, undervolting, or the like, or combinations thereof.

FIG. 3A illustrates example operations that may be performed by the application thread tracker of FIG. 2 , according to various embodiments.

The driver, e.g., application thread tracker 211, may register with the operating system to obtain the notifications such as those shown in “driver initialization” functional block 301, e.g., application load notifications, process create/delete notifications, thread create/delete notifications. The driver, e.g., application thread tracker 211, may initialize an empty thread tracker list.

Function block 302 illustrates processes that may be performed by the driver, e.g., application thread tracker 211, at application run-time. For instance, when the application is launched, the operating system may notify the driver, e.g., application thread tracker 211.

The driver, e.g., application thread tracker 211, may perform filtering responsive to receiving notifications as shown in diamonds 305 and 306 to determine whether to track an application, or not. The driver, e.g., application thread tracker 211, may determine whether the application is an executable in diamond 305. In diamond 306, if the launched application is not an executable in an operating system folder, e.g., a Windows® folder, then the application may be a user mode application, and as such, the application is to be tracked.

In block 307, the thread tracker list may be updated. The thread tracker may store every application of interest from application launch (remaining after the filtering) by the application name and its internal identifiers that are used by the OS scheduler (process ID or “PID” and thread ID or “TID”, which uniquely identify every executable piece of code of that application).

An illustrated “mutex” function 308 refers to a mutually exclusive object, to prevent data structure corruption (so that only one piece of code can access the tracking list at any given point in time).

Notifications corresponding to an application executing (after launch) are also shown in FIG. 3A, and these events can also result in threads being added to the thread tracker list in block 307.

FIG. 3B illustrates example operations that may be performed by the monitoring loop of FIG. 2 .

In block 310, the driver, e.g., monitoring loop 213, may check, according to a configurable interval (say an interval of N seconds), whether the user has changed preferences related to the favored core process. For instance, the application with the user interface enables the user to select which applications may use favored cores, and these settings may be changed by the user at any time. For instance, a ranking of the favored cores could change based on performance customization by a user, e.g., overclocking, underclocking, overvolting, undervolting, or the like, or combinations thereof. In some embodiments, the check in block 310 monitors for any parameter changed via the application with the user interface, e.g. any favored core parameter.

If a parameter change is detected, in diamond 311 the driver, e.g., monitoring loop 213, may check whether the registry has been changed. If a change is detected, a reset of a driver state machine may be performed, as shown in block 313. In some embodiments, the reset may include thread utilization recalculations (e.g., recalculating per-thread utilization as needed), unaffinitizition (e.g., unaffinitizing all threads as needed), checking for hardware favor core status change (e.g., favored core list, enable changed or not), checking for affinitization enabled change or not (e.g., check affinitization enable changed or not), registry updates, affinitization timer restarts and/or stops, or the like, or combinations thereof.

FIG. 3C illustrates example operations that may be performed by the affinitization control loop of FIG. 2 , according to various embodiments.

In block 320, an affinitization timer event may occur (which may be based on a configurable interval such as an evaluation interval parameter in the registry). In diamond 322, the driver, e.g., monitoring loop 213, may determine whether demand is checked for all threads (in the tracker list). If not, for a remaining thread in the tracker list, the driver, e.g., monitoring loop 213, in block 323, may calculate utilization (e.g., processor and/or core utilization), and in diamond 324, may determine whether the utilization is greater than a threshold, e.g., determines whether the utilization is greater than or equal to the parameter “utilizationthresholdpercent”, which may be 90% in an embodiment. If the thread is in a ForeGround application or inclusion list for the favored core in diamond 325, then in block 326 the thread may be marked as a demanding thread (of interest), and the number of the demanding threads counter may be increased.

In diamond 327, the driver, e.g., monitoring loop 213, may determine whether a counter of the number of demanding threads counter is not greater than a count of physical cores. If the count is greater, then in block 328 the driver, e.g., monitoring loop 213, may unaffinitize any previously driver-affinitized threads.

In block 329, the driver, e.g., monitoring loop 213, may sort demanding threads in the tracker list, e.g., rank the threads. The ranking may be based on whether the thread is a user-selected application (from a list of the application with the user interface) and/or in focus (for instance a user-selected application that is also in focus may be ranked higher than a user-selected application that is not in focus).

In diamond 331, the driver, e.g., monitoring loop 213, may determine whether all demanding threads are affinitized to a favored core. If not, in block 332 the driver, e.g., monitoring loop 213, may get a next demanding thread from the tracker list, and in block 333 get a next favored cover from a favored core list. In block 334 the driver, e.g., monitoring loop 213, may affinitize the thread to the core.

FIGS. 4A-B illustrate an example of pseudo code to implement a module of the Power Control Unit (PCU) of the system of FIG. 1 , according to various embodiments.

Software that the PCU executes may be referred to as p-code. Blocks 401-410 illustrate portions of the example pseudo code of a module of the p-code to determine work placement on processor cores.

Block 401 illustrates example definitions. Now may be the current time stamp, and entry delay, exit delay, and loop delay—may be parameters that can be set. Entry delay may be the time to wait after the operating system assigns work through a core to do any migration. Exit delay may be the time to wait after migration before doing another migration. These may prevent thrashing. Loop delay may be the time to wait between polls for a new schedule.

Block 402 may be a check to determine whether the loop delay is met. In an example, p-codes slowest poll is about one millisecond. This loop may execute every one millisecond by default, but the loop delay timer may be used to specify longer than that, if desired. If there has been no change in the number of cores that are running, or no change in the cores that are running that are currently active, then the process may wait until the next round of the loop.

Block 403 shows assignments of information to be used in the process. The value “R” may be the number of running cores that have something scheduled on them right now. Fast stack may be a stack of fastest R cores with the fastest of the cores on the top of the stack, e.g., the core with the highest frequency based on the variation at the top of the stack.

Block 404 may be a condition based on whether the operating system ability is enabled to request specific levels of performance—or power, for a particular piece of work. For example, whether a first predetermined mode is available (in the first predetermined mode the operating system is able to request from the hardware a specific level of performance of each core for a piece of work). This ability may be referred to herein as “HWP”, or Intel® Speed Shift Technology. In an example the conditional check may be whether the predetermined mode, e.g., HWP, is present. If this ability is present, e.g., if hardware P is present, a slow stack of the cores that are actually running may be created with the cores sorted with those with the highest requested performance for their work at the top of the stack and the lowest requested performance for their work at the bottom of the stack. If the predetermined mode is present, the condition is whether the members of the fast stack are the same as the numbers of the slow stack, and in the same order.

Block 405 may be another condition based on whether or not the predetermined mode is present. Without this ability, e.g., for a second different mode, slow stack is defined as the stack of actually running cores with the slowest at the top of the stack. If the predetermined mode is not present, the condition may be whether the members of the fast stack are the same as the numbers of the slow stack regardless of order on the stack.

Block 406 may pop cores from the fast stack. If the popped core is sitting idle and the time-outs have been met, then work may be migrated from the slow stack to a faster core. The migrated work may be the work that is running on the slowest available core. If the popped core of the fast stack is already running and the predetermined mode is not available, then the process may repeat another iteration for the next topmost core of the fast stack. If the predetermined mode is available, the process may take a ranking into account. Similarly, if timeouts are not met, e.g., the core's last migration time, plus the exit delay is greater than now, the process may move to a next core in the fast stack.

In block 407, while the selected core is not running, and while the slow stack is not empty, a core may be popped off the slow stack. This core may be referred to as the victim core because it is the slowest core still being considered (i.e., the work on that core is a victim of being on a slow core). If the predetermined mode is available, the process may determine whether or not migration would realize more performance than that workload is requesting. If the candidate core's performance level is greater than the requested performance level of the core that was popped off the slow stack, then migration may be bypassed. In other words, if the target core for migration corresponds to more performance than the operating system is requesting for the given work, then the migration may not be performed. Similarly, if the migration would be onto a core that is already running other work, and the swap of that work to the target core would result in less performance than the operating system is requesting for that work, the migration may not be performed. Similarly, in block 408 migration may not be performed if the core productivity is below a threshold that implies that migration is worthwhile.

In block 409, a migration may be performed, e.g., work may be migrated from the core that was popped off the slow stack to the target. Migration is bypassed if it would result in assigning the victim work to a lower performing core. If the predetermined mode is available and the target core is currently running work, the migration is actually a swap of work between two cores instead of merely migrating work to an idle core.

FIG. 5 illustrates an example process that may be performed by the module of FIG. 1 , according to various embodiments.

In block 5001, the module (which may be a driver in an embodiment) may identify one core of a processor as favored with respect to another core of the processor. In an example, the cores may be architecturally identical, but have different physical characteristics related to manufacturing of the processor. The favored core may be capable of greater instructions per second than the other core, may have better instruction per watt performance, may have a lower voltage, may be more undervoltable (capable of lower power usage while running), or the like, or combinations thereof.

In block 5002, the module may determine whether a demand of a thread corresponding to an operating system and/or the processor is greater than a threshold. In block 5003, the module may affinitize the thread to the identified core if the thread is not already affinitized to the favored core. In an example, affinitization is using an affinity interface of the operating system.

In an example, the module may determine whether a first number of threads having demand greater than the threshold is greater than a second number of running cores of the processor. The module may unaffinitize a thread-core affinitization in response to a determination that the first number is greater than the second number, e.g., may unaffinitize all thread-core affinitizations, such as all thread-core affinitizations corresponding to at least the identified core.

In an example, the module may add the thread to a tracker list in response to a determination that the demand of the thread is greater than the threshold. The module may sort the threads of the tracker list based on at least one of an inclusion list or user request received by a user interface.

In an example, the module may perform a first affinitization of an initial thread of the sorted tracker list to a core of an initial entry in a favored core list. The module may perform a second affinitization of a next thread of the sorted tracker list to a core of a next entry in the favored core list. The module may repeat the second affinitization until all threads of the sorted tracker list are affinitized to a respective one of the cores of the favored core list.

FIG. 6 illustrates another process that may be performed by the module of FIG. 1 , according to various embodiments.

In block 6001, the module (which may be of a power control unit of a processor) may determine whether to migrate a candidate thread of threads associated with an operating system and/or the processor to or from a candidate of cores of the processor. In an example, the cores may be architecturally identical, but have different physical characteristics related to manufacturing of the processor. The favored core may be capable of greater instructions per second than the other core, may have better instruction per watt performance, may have a lower voltage, may be more undervoltable (capable of lower power usage while running), or the like, or combinations thereof.

In block 6002, the module may ascertain whether the operating system includes a predetermined mode. In an example, the predetermined mode may be HWP (hardware-P). In an example, the predetermined mode may be a mode enabling the operating system to request a specific level of performance or power for a particular piece of work.

In block 6003, the module may select the candidate of the cores of the processor based on a result of the ascertaining.

In an example, the module may generate a first ranking of a first group of the cores based on differing physical characteristics of the cores if the operating system includes the predetermined mode, or a second different ranking of a second group of the cores based on the differing physical characteristics of the cores if the operating system does not include the predetermined mode. The module may select the candidate core of the cores from a top of a stack associated with the first or second ranking.

In an example, the module may select a first subset of the cores, wherein each core of the first subset has a corresponding physical characteristic that is different, e.g., greater, than a threshold physical characteristic. A second subset of the cores may include the remaining cores. The module may identify the first or second group at a first time responsive to identifying ones of the cores of the first subset that are running and associated with work scheduled as of the first time.

In an example, the module may identify a third group at a second time responsive to identifying ones of the cores of the second subset that are running as of the first time. The module may identify the candidate thread and the candidate core during an iteration of an iterative migration checking process that corresponds to the first and second times only if the operating system does not include the predetermined mode and members of the second group are the same as members of the third group, or may identify the candidate thread and the candidate core during an iteration of an iterative migration checking process that corresponds to the first and second times only if the operating system does include the predetermined mode and members of the first ranking are the same and in the same order as members of a ranking of the third group.

FIG. 7 illustrates an example computing device that may employ the apparatuses and/or methods described herein, according to various embodiments.

Example computing device 500 may employ the apparatuses and/or methods described herein, in accordance with various embodiments. As shown, computing device 500 may include a number of components, such as one or more processor(s) 504 (one shown) and at least one communication chip 506.

In various embodiments, the one or more processor(s) 504 each may include one or more processor cores. In various embodiments, the at least one communication chip 506 may be physically and electrically coupled to the one or more processor(s) 504. In further implementations, communication chip 506 may be part of the one or more processor(s) 504. In various embodiments, computing device 500 may include printed circuit board (PCB) 502. For these embodiments, the one or more processor(s) 504 and communication chip 506 may be disposed thereon. In alternate embodiments, the various components may be coupled without the employment of PCB 502.

Depending on its applications, computing device 500 may include other components that may or may not be physically and electrically coupled to PCB 502. These other components include, but are not limited to, a memory controller (not shown), volatile memory (e.g., dynamic random access memory (DRAM) 520), non-volatile memory such as read only memory (ROM) 524, flash memory 522, an I/O controller (not shown), a digital signal processor (not shown), a crypto processor (not shown), a graphics processor 530, one or more antenna 528, a display (not shown), a touch screen display 532, a touch screen controller 546, a battery 536, an audio codec (not shown), a video codec (not shown), a global positioning system (GPS) device 540, a compass 542, an accelerometer (not shown), a gyroscope (not shown), a speaker 550, a camera 552, and a mass storage device (such as hard disk drive, a solid state drive, compact disk (CD), digital versatile disk (DVD)) (not shown), and so forth.

In some embodiments, one or more processor(s) 504, flash memory 522, and/or a storage device (not shown) may include associated firmware (not shown) storing programming instructions configured to enable computing device 500, in response to execution of the programming instructions by one or more processor(s) 504, to practice all or selected aspects of the methods described herein. For example, the programming instructions may implement the earlier described driver with references to the respective ones of FIGS. 1-6 . In various embodiments, these aspects may additionally or alternatively be implemented using hardware separate from one or more processor(s) 504, flash memory 512, or storage device 511. For example, the alternate hardware may include the earlier described power control unit equipped with code to perform the operations earlier described with references to the respective ones of FIGS. 1-6 .

Communication chips 506 may enable wired and/or wireless communications for the transfer of data to and from the computing device 500. The term “wireless” and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a non-solid medium. The term does not imply that the associated devices do not contain any wires, although in some embodiments they might not. Communication chip 506 may implement any of a number of wireless standards or protocols, including but not limited to IEEE 702.20, Long Term Evolution (LTE), LTE Advanced (LTE-A), General Packet Radio Service (GPRS), Evolution Data Optimized (Ev-DO), Evolved High Speed Packet Access (HSPA+), Evolved High Speed Downlink Packet Access (HSDPA+), Evolved High Speed Uplink Packet Access (HSUPA+), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Digital Enhanced Cordless Telecommunications (DECT), Worldwide Interoperability for Microwave Access (WiMAX), Bluetooth, derivatives thereof, as well as any other wireless protocols that are designated as 3G, 5G, 5G, and beyond. Computing device 500 may include a plurality of communication chips 506. For instance, a first communication chip 506 may be dedicated to shorter range wireless communications such as Wi-Fi and Bluetooth, and a second communication chip 506 may be dedicated to longer range wireless communications such as GPS, EDGE, GPRS, CDMA, WiMAX, LTE, Ev-DO, and others.

In various implementations, computing device 500 may be a laptop, a netbook, a notebook, an ultrabook, a smartphone, a computing tablet, a personal digital assistant (PDA), an ultra-mobile PC, a mobile phone, a desktop computer, a server, a printer, a scanner, a monitor, a set-top box, an entertainment control unit (e.g., a gaming console or automotive entertainment unit), a digital camera, an appliance, a portable music player, or a digital video recorder. In further implementations, computing device 500 may be any other electronic device that processes data.

Any combination of one or more computer usable or computer readable medium(s) may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer usable program code may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object-oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

EXAMPLES

Example 1 is an apparatus for computing including determination of processor core work placement is provided. The apparatus may include a processor including: a plurality of architecturally identical cores, wherein a first core of the plurality of architecturally identical cores has a first physical characteristic and a second core of the plurality of architecturally identical cores has a second physical characteristic that is different than the first physical characteristic; and a favored core module to be operated by the processor. The favored core module may be to: identify one of the first and second cores as favored with respect to the other of the first and second cores; determine whether a demand of a thread is greater than a threshold; and in response to a determination that the demand of the thread is greater than the threshold, affinitize the thread to the identified core if the thread is not already affinitized to the favored core.

Example 2 includes the subject matter of example 1, and the one of the first and second physical characteristics that corresponds to the favored core includes a first voltage that is lower than a second voltage of the other of the first and second physical characteristics.

Example 3 includes the subject matter of any of examples 1-2, and the first and second cores are associated with a same operating frequency.

Example 4 includes the subject matter of any of examples 1-2, and the first and second cores are associated with different operating frequencies.

Example 5 includes the subject matter of any of examples 1-4, and the favored core corresponds to a user-selection input via a user interface.

Example 6 includes the subject matter of any of examples 1-5, and the favored core corresponds to data of a fuse table.

Example 7 includes the subject matter of any of examples 1-6, and the favored core module is to: determine whether a first number of threads having demand greater than the threshold is greater than a second number of running cores of the processor; and in response to a determination that the first number is greater than the second number, unaffinitize a thread-core affinitization.

Example 8 includes the subject matter of any of examples 1-7, and the favored core module is to: in response to the determination that the first number is greater than the second number, unaffinitize all thread-core affinitizations corresponding to at least the identified core.

Example 9 includes the subject matter of any of examples 1-8, and the favored core module is to: in response to a determination that the demand of the thread is greater than the threshold, add the thread to a tracker list; sort the threads of the tracker list based on at least one of an inclusion list or user request received by a user interface.

Example 10 includes the subject matter of any of examples 1-9, and the favored core module is to: perform a first affinitization of an initial thread of the sorted tracker list to a core of an initial entry in a favored core list; perform a second affinitization of a next thread of the sorted tracker list to a core of a next entry in the favored core list; and repeat the second affinitization until all threads of the sorted tracker list are affinitized to a respective one of the cores of the favored core list.

Example 11 is a computer-readable medium for computing including determination of processor core work placement, the instructions having instructions stored thereon that, in response to execution by a processing device, cause the processing device to perform operations, to: identify one of a plurality of cores of a processor as favored with respect to another of the plurality of cores; determine whether a demand of a thread corresponding to the processor is greater than a threshold; and in response to a determination that the demand of the thread is greater than the threshold, affinitize the thread to the identified core if the thread is not already affinitized to the favored core.

Example 12 includes the subject matter of example 11, and the operations are further to: determine whether a first number of threads having demand greater than the threshold is greater than a second number of running cores of the processor; and in response to a determination that the first number is greater than the second number, unaffinitize a thread-core affinitization.

Example 13 includes the subject matter of any of examples 11-12, and the operations are further operable to: in response to the determination that the first number is greater than the second number, unaffinitize all thread-core affinitizations corresponding to at least the identified core.

Example 14 includes the subject matter of any of examples 11-13, and operations are further operable to: in response to a determination that the demand of the thread is greater than the threshold, add the thread to a tracker list; and sort the threads of the tracker list based on at least one of an inclusion list or user request received by a user interface.

Example 15 includes the subject matter of any of examples 11-14, and the operations are further operable to: perform a first affinitization of an initial thread of the sorted tracker list to a core of an initial entry in a favored core list; perform a second affinitization of a next thread of the sorted tracker list to a core of a next entry in the favored core list; and repeat the second affinitization until all threads of the sorted tracker list are affinitized to a respective one of the cores of the favored core list.

Example 16 is an apparatus for computing including determination of determine processor core work placement of threads associated with an operating system, the apparatus comprising: a plurality of cores, wherein a first core of the plurality of cores has a first physical characteristic and a second core of the plurality of cores has a second physical characteristic that is different than the first physical characteristic; and a power control unit to: determine whether to migrate a candidate thread of the threads to or from a candidate of the plurality of cores; ascertain whether the operating system includes a predetermined mode; and select the candidate of the plurality of cores based on a result of the ascertainment.

Example 17 includes the subject matter of example 16, and the power control unit is further to: generate a first ranking of a first group of the plurality of cores based on differing physical characteristics of the plurality of cores if the operating system includes the predetermined mode; generate a second ranking of a second group of the plurality of cores based on the differing physical characteristics of the plurality of cores if the operating system does not include the predetermined mode, wherein the second ranking is different than the first ranking; and select the candidate core of the plurality of cores from a top of the first or second ranking.

Example 18 includes the subject matter of any of examples 16-17, and the power control unit is further to: select a first subset of the plurality of cores, wherein each core of the first subset has a corresponding physical characteristic greater than a threshold physical characteristic; and wherein a second subset of the plurality of cores includes the remaining cores; form the first or second group at a first time responsive to identifying ones of the cores of the first subset that are running and associated with work scheduled as of the first time.

Example 19 includes the subject matter of any of examples 16-18, and the power control unit is further to: form a third group at a second time responsive to identifying one of the cores of the second subset that are running as of the first time.

Example 20 includes the subject matter of any of examples 16-19, and the power control unit is further to: identify the candidate thread and the candidate core during an iteration of an iterative migration checking process that corresponds to the first and second times only if the operating system does not include the predetermined mode and members of the second group are the same as members of the third group; and identify the candidate thread and the candidate core during an iteration of an iterative migration checking process that corresponds to the first and second times only if the operating system does include the predetermined mode and members of the first ranking are the same and in the same order as members of a ranking of the third group.

Example 21 is a method for computing, including determination of processor core work placement of threads associated with an operating system with respect to a plurality of architecturally identical cores, the method comprising: determining whether to migrate a candidate thread of the threads to or from a candidate of the plurality of architecturally identical cores; ascertaining whether the operating system includes a predetermined mode; and selecting the candidate of the plurality of architecturally identical cores based on a result of the ascertaining.

Example 22 includes the subject matter of example 21, and generating a first ranking of a first group of the plurality of architecturally identical cores based on differing physical characteristics of the plurality of architecturally identical cores if the operating system includes the predetermined mode; generating a second ranking of a second group of the plurality of architecturally identical cores based on the differing physical characteristics of the plurality of architecturally identical cores if the operating system does not include the predetermined mode, wherein the second ranking is different than the first ranking; and selecting the candidate core of the plurality of architecturally identical cores from a top of the first or second ranking.

Example 23 includes the subject matter of any of examples 20-21, selecting a first subset of the plurality of architecturally identical cores, wherein each core of the first subset has a corresponding physical characteristic greater than a threshold physical characteristic; and wherein a second subset of the plurality of architecturally identical cores includes the remaining cores; forming the first or second group at a first time responsive to identifying ones of the cores of the first subset that are running and associated with work scheduled as of the first time.

Example 24 includes the subject matter of any of examples 21-23 and forming a third group at a second time responsive to identifying one of the cores of the second subset that are running as of the first time; identifying the candidate thread and the candidate core during an iteration of an iterative migration checking process that corresponds to the first and second times only if the operating system does not include the predetermined mode and members of the second group are the same as members of the third group; and identifying the candidate thread and the candidate core during an iteration of an iterative migration checking process that corresponds to the first and second times only if the operating system does include the predetermined mode and members of the first ranking are the same and in the same order as members of a ranking of the third group.

Example 25 includes the subject matter of any of examples 21-24, wherein the predetermined mode is a mode enabling the operating system to request a specific level of performance or power for a particular piece of work.

Example 26 is an apparatus determination of processor core work placement, the apparatus comprising: means for identifying one of a plurality of cores of a processor as favored with respect to another of the plurality of cores; means for determining whether a demand of a thread corresponding to the processor is greater than a threshold; and means for affinitizing the thread to the identified core if the thread is not already affinitized to the favored core in response to a determination that the demand of the thread is greater than the threshold.

Example 27 includes the subject matter of example 26, and means for determining whether a first number of threads having demand greater than the threshold is greater than a second number of running cores of the processor; and means for unaffinitizing a thread-core affinitization in response to a determination that the first number is greater than the second number.

Example 28 includes the subject matter of any of examples 26-27, and means for unaffinitizing all thread-core affinitizations corresponding to at least the identified core in response to the determination that the first number is greater than the second number.

Example 29 includes the subject matter of any of examples 26-28, and adding the thread to a tracker list in response to a determination that the demand of the thread is greater than the threshold; and sorting the threads of the tracker list based on at least one of an inclusion list or user request received by a user interface.

Example 30 includes the subject matter of any of examples 26-29, and performing a first affinitization of an initial thread of the sorted tracker list to a core of an initial entry in a favored core list; performing a second affinitization of a next thread of the sorted tracker list to a core of a next entry in the favored core list; and repeating the second affinitization until all threads of the sorted tracker list are affinitized to a respective one of the cores of the favored core list. 

What is claimed is:
 1. An apparatus, comprising: a processor including a plurality of cores and a core assignment module operable by the processor to: identify a ranked list of a subset of cores of the plurality of cores that have different physical characteristics than remaining core(s) of the plurality of cores; determine whether a first count of thread(s) selected for optimization is less than or equal to a second count of the cores of the ranked list; in response to a determination that the first count is less than or equal to the second count: perform a first affinitization of an initial thread of the selected thread(s) to a core of an initial entry in the ranked list; and perform one or more second affinitizations of any one or more next threads, respectively, of the selected thread(s) to one or more cores of one or more next entries in the ranked list, respectively; and in response to a determination that the first count is greater than the second count, unaffinitize at least one thread-core affinitization of at least one uncompleted thread that is different than the thread(s) selected for optimization, the at least one thread-core affinitization corresponding to the subset of core(s).
 2. The apparatus of claim 1, wherein the cores of the ranked list have first operating voltages, respectively, that are lower than one or more second operating voltages, respectively, of the remaining core(s).
 3. The apparatus of claim 2, wherein at least one core of the cores of the ranked list is associated with a same operating frequency as at least one of the remaining core(s).
 4. The apparatus of claim 2, wherein at least one core of the ranked list is associated with a different operating frequency than at least one core of the remaining core(s).
 5. The apparatus of claim 1, wherein at least one of the cores of the ranked list corresponds to a user-selection input via a user interface.
 6. The apparatus of claim 1, wherein at least one of the cores of the ranked list corresponds to data of a fuse table.
 7. The apparatus of claim 1, wherein unaffinitize at least one thread-core affinitization comprises unaffinitize all thread-core affinitizations corresponding to at least one core of the cores of the ranked list.
 8. The apparatus of claim 7, wherein the core assignment module is further to: rank the thread(s) selected for optimization based on at least one of an inclusion list or user request received by a user interface.
 9. The apparatus of claim 1, wherein the core assignment module is further to, for each thread of the thread(s) selected for optimization, in response to a determination that a demand of the thread is greater than a threshold: add the thread to a tracker list and sort the threads of the tracker list based on an inclusion list or a user request received via a user interface; and select the sorted thread for affinitization.
 10. The apparatus of claim 1, wherein the threads selected for optimization are identified from a ranked list of threads.
 11. A hardware memory having instructions stored thereon that, in response to execution by a processing device, cause the processing device to perform operations, to: identify a ranked list of a subset of cores of a plurality of cores that have different physical characteristics than remaining core(s) of the plurality of cores; determine whether a first count of thread(s) selected for optimization based on processor core assignment is less than or equal to a second count of the cores the ranked list; and in response to a determination that the first count is less than or equal to the second count: perform a first affinitization of an initial thread of the selected thread(s) to a core of an initial entry in the list; perform one or more second affinitizations of any one or more next threads, respectively, of the selected thread(s) to one or more cores of one or more next entries in the ranked list, respectively; and in response to a determination that the first count is greater than the second count: unaffinitize at least one thread-core affinitization of second thread(s) that are different than the first thread(s), wherein the second thread(s) comprise at least one uncompleted thread, the at least one thread-core affinitization corresponding to the subset of core(s).
 12. The hardware memory of claim 11, wherein unaffinitize at least one thread-core affinitization comprises unaffinitize all thread-core affinitizations corresponding to at least one core of the cores of the ranked list.
 13. The hardware memory of claim 12, wherein operations are further operable to: rank the selected thread(s) based on at least one of an inclusion list or user request received by a user interface.
 14. The hardware memory of claim 11, wherein the operations include: for each thread of the thread(s) selected for optimization, in response to a determination that a demand of the thread is greater than a threshold: add the thread to a tracker list and sort the threads of the tracker list based on an inclusion list or a user request received via a user interface; and select the sorted thread for affinitization.
 15. The hardware memory of claim 11, wherein the cores of the ranked list have one or more first operating voltages, respectively, that are lower than one or more second operating voltages, respectively, of the remaining core(s).
 16. The hardware memory of claim 15, wherein the at least one core of the cores of the ranked list is associated with a same operating frequency as at least one core of the remaining core(s).
 17. The hardware memory of claim 15, wherein the at least one core of the cores of the ranked list is associated with a different operating frequency than at least one core of the remaining core(s).
 18. The hardware memory of claim 11, wherein at least one of the cores of the ranked list corresponds to a user-selection input via a user interface.
 19. The hardware memory of claim 11, wherein at least one of the cores of the ranked list corresponds to data of a fuse table.
 20. The hardware memory of claim 11, wherein the threads selected for optimization are identified from a ranked list of threads. 